Voicemail management with multi-number phones

ABSTRACT

A computer-implemented method for managing voicemails includes receiving, at an intermediate server communicatively coupled to a mobile phone associated with a first phone number corresponding to a first contact group and a second phone number corresponding to a second contact group, a request to receive an incoming call associated with a caller phone number. The intermediate server identifies a contact group associated with the request. The identified contact group comprises the first contact group in response to the received request corresponding to the first phone number, and the identified contact group comprises the second contact group in response to the received request corresponding to the second phone number. The intermediate server selects a voicemail setting based on the identified contact group. In response to determining to route the incoming call to voicemail, the voicemail is configured based at least in part on the selected voicemail setting.

CROSS-REFERENCE TO RELATED APPLICATION(S)

This application claims priority under 35 U.S.C. §119(e) to U.S.Provisional Patent Application Ser. No. 62/184,174, “CommunicationEnvironment with Unified Communication Interfaces,” filed Jun. 24, 2015,which is incorporated herein by reference in its entirety.

BACKGROUND

1. Field of the Disclosure

This disclosure pertains in general to communications, and morespecifically to voicemail management in a mobile phone communicationenvironment enabling a unified communication interface for multiplephone numbers and contact groups within a single device.

2. Description of the Related Art

Mobile devices including smart phones and tablets have becomeubiquitous. People use mobile devices for personal reasons to stayconnected with family and friends, and also for business purposes. It iscumbersome to carry multiple mobile devices for different uses.Nevertheless, mobile devices are usually associated with one ID (e.g., aSubscriber Identity Module (SIM), an International Mobile SubscriberIdentity (IMSI), an Electronic Serial Number (ESN), and the like), andare typically associated with one phone number. When using such devicesfor multiple purposes, it is complex to manage and track communicationsand costs, to safeguard secured or private communications, and tomaintain work and life balance. Each individual typically has multiplephone numbers (e.g. office, mobile, home) for different purposes. As aresult, communications between people are fragmented across multiplenumbers.

SUMMARY

One embodiment of the computer-implemented method for managing incomingcalls comprises receiving, at an intermediate server communicativelycoupled to a mobile phone associated with a first phone numbercorresponding to a first contact group and a second phone numbercorresponding to a second contact group, a request to receive anincoming call associated with a caller phone number. The requestcorresponds to the first phone number or the second phone number. Inresponse to receiving the request to receive the incoming call, theintermediate server identifies a contact group associated with therequest. The identified contact group comprises the first contact groupin response to the received request corresponding to the first phonenumber, and the identified contact group comprises the second contactgroup in response to the received request corresponding to the secondphone number. The intermediate server selects a notification based onthe identified contact group, wherein the selected notificationcomprises a first notification in response to the identified contactgroup comprising the first contact group, and wherein the selectednotification comprises a second notification in response to theidentified contact group comprising the second contact group. The firstnotification is different from the second notification. The intermediateserver modifies the request to receive an incoming call to include theselected notification and routes the modified request to the mobilephone.

One embodiment of a non-transitory computer-readable storage mediumstoring executable computer program instructions for managing incomingcalls that, when executed by a hardware processor, performing stepscomprising receiving, at an intermediate server communicatively coupledto a mobile phone associated with a first phone number corresponding toa first contact group and a second phone number corresponding to asecond contact group, a request to receive an incoming call associatedwith a caller phone number. The request corresponds to the first phonenumber or the second phone number. In response to receiving the requestto receive the incoming call, the intermediate server identifies acontact group associated with the request. The identified contact groupcomprises the first contact group in response to the received requestcorresponding to the first phone number, and the identified contactgroup comprises the second contact group in response to the receivedrequest corresponding to the second phone number. The intermediateserver selects a notification based on the identified contact group,wherein the selected notification comprises a first notification inresponse to the identified contact group comprising the first contactgroup, and wherein the selected notification comprises a secondnotification in response to the identified contact group comprising thesecond contact group. The first notification is different from thesecond notification. The intermediate server modifies the request toreceive an incoming call to include the selected notification and routesthe modified request to the mobile phone.

One embodiment of a system for managing incoming calls comprising anintermediate server communicatively coupled to a mobile phone associatedwith a first phone number and a second phone number. The intermediateserver comprises a non-transitory computer-readable storage mediumstoring executable instructions and one or more hardware processorsconfigured to execute the instructions to perform steps comprisingreceiving, at an intermediate server communicatively coupled to a mobilephone associated with a first phone number corresponding to a firstcontact group and a second phone number corresponding to a secondcontact group, a request to receive an incoming call associated with acaller phone number. The request corresponds to the first phone numberor the second phone number. In response to receiving the request toreceive the incoming call, the intermediate server identifies a contactgroup associated with the request. The identified contact groupcomprises the first contact group in response to the received requestcorresponding to the first phone number, and the identified contactgroup comprises the second contact group in response to the receivedrequest corresponding to the second phone number. The intermediateserver selects a notification based on the identified contact group,wherein the selected notification comprises a first notification inresponse to the identified contact group comprising the first contactgroup, and wherein the selected notification comprises a secondnotification in response to the identified contact group comprising thesecond contact group. The first notification is different from thesecond notification. The intermediate server modifies the request toreceive an incoming call to include the selected notification and routesthe modified request to the mobile phone.

One embodiment of the computer-implemented method for managing incomingcalls comprises receiving, at an intermediate server communicativelycoupled to a mobile phone associated with a first phone numbercorresponding to a first contact group and a second phone numbercorresponding to a second contact group, a request to receive anincoming call associated with a caller phone number. The requestcorresponds to the first phone number or the second phone number. Inresponse to receiving the request to receive the incoming call, theintermediate server identifies a contact group associated with therequest. The identified contact group comprises the first contact groupin response to the received request corresponding to the first phonenumber, and the identified contact group comprises the second contactgroup in response to the received request corresponding to the secondphone number. The intermediate server selects a notification based onthe phone number corresponding to the request, wherein the selectednotification comprises a first notification in response to theidentified contact group comprising the first contact group, and whereinthe selected notification comprises a second notification in response tothe identified contact group comprising the second contact group. Thefirst notification is different from the second notification. Theintermediate server modifies the request to receive an incoming call toinclude the selected notification and routes the modified request to themobile phone.

The features and advantages described in the specification are not allinclusive and, in particular, many additional features and advantageswill be apparent to one of ordinary skill in the art in view of thedrawings and specification. Moreover, it should be noted that thelanguage used in the specification has been principally selected forreadability and instructional purposes, and may not have been selectedto delineate or circumscribe the inventive subject matter.

BRIEF DESCRIPTION OF THE DRAWINGS

The teachings of the present disclosure can be readily understood byconsidering the following detailed description in conjunction with theaccompanying drawings.

FIG. (FIG.) 1 is a high-level block diagram of a system forcommunications, according to one embodiment.

FIG. 2 is a block diagram illustrating an example unified communicationservice, according to one embodiment.

FIG. 3 illustrates a sequence diagram of an exemplary outgoing call,according to one embodiment.

FIG. 4 illustrates a sequence diagram of an exemplary incoming callmanagement module, according to one embodiment.

FIG. 5 illustrates a sequence diagram of an exemplary voicemailmanagement module 212, according to one embodiment.

FIG. 6 illustrates a sequence diagram of an exemplary text managementmodule, according to one embodiment.

FIG. 7 illustrates a sequence diagram of an exemplary text managementmodule, according to one embodiment.

FIG. 8 illustrates a sequence diagram of an exemplary text managementmodule, according to one embodiment.

FIG. 9 illustrates a sequence diagram of an exemplary text managementmodule, according to one embodiment.

FIG. 10 illustrates a sequence diagram of an exemplary billingmanagement module, according to one embodiment.

DETAILED DESCRIPTION

The Figures (FIG.) and the following description relate to variousembodiments by way of illustration only. It should be noted that fromthe following discussion, alternative embodiments of the structures andmethods disclosed herein will be readily recognized as viablealternatives that may be employed without departing from the principlesdiscussed herein. Reference will now be made in detail to severalembodiments, examples of which are illustrated in the accompanyingfigures. It is noted that wherever practicable similar or like referencenumbers may be used in the figures and may indicate similar or likefunctionality.

Embodiments relate to unified communication interfaces that provide andmanage communication services. A unified communication service providescommunication services to one or more of the users that arecomplementary to the communication services provided by the serviceproviders of the users. A unified communication service allows users tounify activities across different interfaces. A user may register andconfigure the service to receive various combinations of communicationservices provided by the unified communication service. A unifiedcommunication service stores and manages a user's contacts. A user'scontact may be assigned to a contact group including contacts of thesame type. The user may also create, edit, or manage a contact groupincluding a set of contacts and the associated contact group settings. Aunified communication service manages different types of communicationservices (e.g., calls, SMS, MMS, voicemails, etc.) based on thecontacts. The unified communication service allows a user to configureand manage different billing policies and determine costs of variouscommunications. In addition, the unified communication service managesprivacy settings for various communication services; a user can makevarious communications private to other users. In addition, a unifiedcommunication interface may allow integration with business software orinterfaces such as customer relationship management (CRM) systems.

FIG. 1 is a high-level block diagram of a system 100 for communications,according to one embodiment. The system 100 includes a network 110 andusers 102 a-n. The user 102 a may communicate one or more of the users102 b-n via a phone (or “cell phone” or “mobile device” hereinafter)associated with each user (not illustrated in the embodiment of FIG. 1).One or more of the users 102 b-102 n may be contacts of the user 102 a.A contact of the user 102 a is a person whose identity (e.g., name,phone number, social network ID) is known to the user 102 a. Forexample, a record of a contact's name as well as one or more phonenumbers including cell phone number, work phone number, or home phonenumber may be associated and stored as a record on the cell phone of theuser 102 a. The network 110 enables communications among the users 102a-n. The network 110 can be a cellular network based on technologies orprotocols such as a Global System for Mobile Communications (GSM),General Packet Radio Service (GPRS), Enhanced Data Rates for GSMEvolution (EDGE), Universal Mobile Telecommunications System (UMTS),Evolution-Data Optimized (EV-DO), Code Division Multiple Access (CDMA),Long Term Evolution (LTE), etc. The network 110 may be a wireless or awired network. The network 110 can include links based on technologiesincluding Ethernet, 802.11, worldwide interoperability for microwaveaccess (WiMAX), 4G, digital subscriber line (DSL), asynchronous transfermode (ATM), InfiniBand, PCI Express Advanced Switching, multiprotocollabel switching (MPLS), the transmission control protocol/Internetprotocol (TCP/IP), the User Datagram Protocol (UDP), the hypertexttransport protocol (HTTP), the simple mail transfer protocol (SMTP), thefile transfer protocol (FTP), etc.

The users 102 a-n (“users 102”) are connected to the network via theirrespective service providers 104 a-n (“service providers 104”). Theservice providers 104 provide services (e.g., radio spectrum allocation,network infrastructure, back haul infrastructure, billing, customercare, provisioning computer systems) to the users 102 to access thenetwork 110. A service provider of the service providers 104 b-n may bethe same as or different from the service provider 104 a, and may be inthe same region as or at a different region from the service provider104 a. For example, the service provider 104 a and the service provider104 b are the same first local carrier in the U.S., the service provider104 c is a different second local carrier in the U.S., and the serviceprovider 104 n is a local carrier in France. As used herein, “serviceprovider” refers to an entity that provides, through a combination ofcommunicative hardware and software systems, a wireless communicativeinterface for use by a mobile device. Examples of service providesinclude AT&T, Verizon Wireless, Sprint, T-Mobile, and the like.

The unified communication service 106 provides communication services toone or more of the users 102 that are complementary to the communicationservices provided by the service providers 104. For example, the unifiedcommunication service 106 can manage the communications among the users102. A user may register with the unified communication service 106 andcan select or subscribe to various communication services provided bythe unified communication service 106 through a platform or interfaceprovided by the unified communication service 106. For example, theunified communication service 106 can manage a user's contacts byassociating each contact with a particular set or group of contacts, canmanage outgoing and incoming calls for an associated device, can manageshort message services (SMSs) and multimedia message services (MMSs),can provide voicemail services, can manage billing policies anddevice/communication service usage, can manage privacy policies for auser, etc. The user may access the unified communication service 106 viaa user interface, a website, or an application installed on a device(e.g., a mobile device such as a cellphone, a smart phone, a tablet, ora laptop; a wearable device such as a watch or a glass; a laptop or adesktop; or a vehicle such as a car). The unified communication service106 is described in great detail in conjunction with FIG. 2. It shouldbe noted that in some embodiments, the unified communication service 106is implemented by one or more service providers 104, for instance inhardware, software, or both controlled by a service provider 104 andconfigured to perform the functionalities described herein.

FIG. 2 is a block diagram illustrating an example unified communicationservice 106, according to one embodiment. The unified communicationservice 106 includes specialized communication hardware configured toperform the communication services described herein. The unifiedcommunication service 106 also includes a computing system with ahardware processor adapted to execute computer modules for providing thefunctionality described herein. As used herein, the term “module” refersto computer program instruction and other logic for providing aspecified functionality. A module can be implemented in hardware,firmware, and/or software. A module can include one or more processes,and/or be provided by only part of a process. A module is typicallystored on a storage device, loaded into a memory, and executed by aprocessor. The illustrated unified communication service 106 includes auser management module 202, a user and contact store 204, a contactmanagement module 206, an outgoing call management module 208, aninbound call management module 210, a voicemail management module 212, atext management module 214, a billing management module 216, a privacymanagement module 218, a billing account store 220, a home numbermanagement module 222, and a business integration module 224. Those ofskill in the art will recognize that other embodiments can havedifferent and/or other modules than the ones described here, and thatthe functionalities can be distributed among the modules in a differentmanner. As described herein, a user may be an individual or an entity.

The unified communication service 106 allows users to unify activitiesacross different interfaces. For example, applications installed on auser's device and a user's web activities over a browser can be accessedvia the unified communication service 106. Different mediums ofcommunications (e.g., calls, text messages, emails, etc.) with differentcontacts are organized by contact identity rather than phone numbers oraddresses. All activities in the network are managed and accessed by theunified communication service 106. For example, the unifiedcommunication service 106 may provide a threaded view per contactshowing all activities with that contact over all activity mediums thatgo through the network 110 regardless of the device used by the contactor the medium through which the activity occurs. For example, a user maycall a contact (Tom), may receive a voicemail from Tom, and may receivetext messages from Tom from the user's web browser all within theunified communications service 106 that shows all the above-mentionedcommunications with Tom regardless of which device the user or Tom uses.The unified communication service 106 may provide a single threaded viewthat integrates communications of different mediums such as calls(to/from one or more phone numbers), messaging (text or instantmessaging), voicemail, email, communications within apps, or any othersuitable type of interaction. Accordingly, the unified communicationservice 106 can provide one continuous thread where a user can accessall communication activities with a contact. The user can switch betweenon/off filters in the view of the threaded communications toinclude/exclude certain mediums. When a contact uses different numbers,that is, when a contact is associated with multiple numbers, the unifiedcommunication service 106 allows a user to merge different threads ofcommunications with this contact into one single thread or to keep themapart (for instance, interactions associated with a personal phonenumber can be kept within a “personal” unified communication thread, andinteractions associated with a work phone number can be kept within a“work” unified communication thread).

The unified communication service 106 allows a user to manage when theuser or associated users (e.g., employees of a company) can receivecommunication services associated with one or more particular numbers.For example, the unified communication service 106 may provide a do notdisturb user interface via which the user can set according to the dayand hour (e.g., DND for Work Number activates at 7 pm each day anddeactivates at 8 am). The unified communication service adjusts the timefor changes in time zone. As one example, a company can set active hoursfor business communications (e.g., phone calls, text messages, etc. fromand to business numbers, emails from and to business email addresses)for selected employees and limit overtime wages.

The user management module 202 allows a user to manage communicationservices, and creates, manages, and stores user information in the userand contact store 204. The user management module 202 may provide aninterface for a user to register, select, and manage communicationservices provided by the unified communication service 106. For example,the user may register to receive communication services provided by theunified communication interface via a website, where the user creates anaccount. The user may register by activating a user application of theunified communication service 106 and creating an account thereafter. Insome embodiments, the user application may be preinstalled on the deviceor integrated with the firmware of the device. The user managementmodule 202 creates a unified communication ID for the user when the userregisters and associates the unified communication ID with the user andstores such association in the user and contact store 204. The unifiedcommunication ID may be linked to one or more phone numbers and may beassociated with one or more devices the user selects to receivecommunication services. The mobile phone that the user registers withthe unified communication service 106 has a phone number with the regioncode (e.g., country code, and/or area code) associated with the deviceID (e.g., Subscriber Identity Module (SIM), International MobileSubscriber Identity (IMSI), Electronic Serial Number (ESN), or otherunique identifier associated with the device hardware).

In addition, the user can opt to link the mobile phone with the unifiedcommunication ID and the unified communication service 106, which inturn can associate the mobile phone with a virtual device ID (a uniqueidentifier assigned to the mobile phone by the unified communicationservice 106). The communication service 106 can then associate themobile phone with a second phone number associated with the virtualdevice ID. As such, the user's mobile phone is linked with two phonenumbers—a first number associated with the device ID and a second numberassociated with the virtual device ID or unified communication ID. Theuser may associate multiple devices with his or her account and aunified communication ID may be associated with multiple devicesassociated with the user's account. The user may further associate hisor her accounts at social network services, messaging services, and thelike with the account at the unified communication service 106 and/orthe unified communication ID. In one embodiment, a user's phone islinked to a work number associated with a virtual device ID or unifiedcommunication ID and a personal number associated with the device ID. Inanother embodiment, a user's phone is linked to a personal numberassociated with a virtual device ID or unified communication ID and awork number associated with the device ID. In some embodiments, a user'sphone is linked to a set of work numbers and a set of personal numbers.

A user may customize the user's account to receive various combinationsof communication services received provided by the unified communicationservice 106. For example, the user may select voice call services, videocall services, SMS services, MMS services, voicemail services, caller IDservices, billing services, privacy services, or any combination thereoffrom the communication services provided by the unified communicationservice 106. The user and contact store 204 stores informationassociated with the user, such as the user's account ID, the unifiedcommunication ID, the virtual device ID, registered devices includingassociated information (e.g., device IDs, device models, serviceproviders, etc.), one or more devices associated with the unifiedcommunication ID or virtual device ID, voicemail boxes and associatedpasswords, voicemail greeting messages, billing accounts (e.g.,corporate, personal), the user's personal information (e.g., birthday,home address, work address, etc.), the user's accounts at social networkservices, the user's accounts at messaging services, the user's contactsand associated information (e.g., a contact's name(s), the contact'sphone number(s) (e.g., home phone number, cellphone number, work phonenumber), the contact's type (e.g., business, friends, family, oracquaintance), the contact's company, the contact's department, thecontact's email, the contact's social network profiles, the contact'sinstant messaging IDs, the contact's chat tool IDs, a call alert type(e.g., ringtone, volume, vibration, mute, or any combination thereof)associated with one of the contact's phone number(s), a SMS alert type(ringtone, volume, vibration, mute, or any combination thereof)associated with one of the contact's phone number(s), an alert type(ringtone, volume, vibration, mute, or any combination thereof)associated with one of the contact's social network update, an instantmessaging alert type (ringtone, volume, vibration, mute, or anycombination thereof) associated with receiving a type of instant messagefrom the contact, an alert type (ringtone, volume, vibration, mute, orany combination thereof) associated with receiving a type of chatmessage from the contact, an alert type (ringtone, volume, vibration,mute, or any combination thereof) associated with receiving a voicemailfrom the contact, a contact's group (e.g., business, work, friends,family, or acquaintance), or whether or not a contact is blocked.) Inaddition, the user and contact store 204 can store one or more contactgroups or sets of contacts, for instance a set of personal contacts anda set of work contacts. Ringtones can be selected from the device'snative ringtones.

In some embodiments, information associated with the user and stored bythe user and contact store 204 may further include subsidiary useraccounts and associated information. For example, an entity's accountmay be stored with employee accounts that are subsidiary to the entity'saccount, or a parent's account may be stored with children's accountsthat are subsidiary to the parent's account. A user may activate ordeactivate a subsidiary account via the user management module 202. Forexample, the user may grant the subsidiary a license to register and usecommunication services provided by the unified communication service 106and selected by the user. Under the license, a subsidiary account may beprohibited from registering and using some communication servicesprovided by the unified communication service 106. When a userdeactivates a subsidiary account, the license is revoked. The user maytrack, monitor, and manage subsidiary accounts. In one embodiment, abusiness may activate a subsidiary account for each of a set ofemployees, enabling the employees to access services provided by theunified communication service 106 and paid for/managed by the business.

The contact management module 206 manages a user's contacts stored inthe user and contact store 204. When a user registers a device with theunified communication service 106, the contact management module 206 mayrecognize the user's contacts stored on the device. The user's contactson the device but not associated with the user and stored in the userand contact store 204 can be copied from the device, associated with theuser and stored in the user and contact store 204. The contactmanagement module 206 may reconcile different contact information storedin the user and contact store 204 and on the device for the same contactand update the contact information accordingly stored in the user andcontact store 204 or on the device. In some embodiments, the contactmanagement module 204 may synchronize contacts of a user among devicesregistered and/or selected by the user. The contact management modulemay provide a user interface through which a user may create, edit, ormanage a contact record storing a contact's information.

A user may also create, edit, or manage a contact group including a setof contacts and the associated contact group settings. Contacts of acontact group have the same contact type. In some embodiments, a contactcan be only assigned to one contact group. In some embodiments, acontact can be assigned to multiple contact groups. Example contactgroups include business contacts, personal contacts, family contacts,friend contacts, contacts of a geographic region, etc. A user mayassociate various device IDs, virtual device IDs, and/or phone numbersof the user with different contact groups. In the aforementioned exampleof a user linking two numbers with the user's mobile phone, the user mayassociate one number with a first contact group (e.g., business) and theother number with a second contact group (e.g., personal). A user mayconfigure and apply a contact group setting to a group such as: an alerttype (ringtone, volume, vibration, mute, or any combination thereof) forreceiving voice calls, video calls, SMSs, MMSs, social network updates,instant messages, chat messages, or voicemails from a contact group; afrequency of receiving alerts associated with a contact group; whetheror not to enable caller ID function for outgoing calls and a phonenumber associated with the mobile device to display to the receivingcontact based on the contact group to which the receiving contactbelongs; whether or not to enable caller ID for incoming calls from acontact and an indication within the caller ID of the contact group towhich the contact belongs; whether or not to block communications fromcontacts within a contact group such that all incoming voice calls,video calls, SMSs, MMSs, social network updates, instant messages, chatmessages, and voicemails, from the contact group cannot be completed, ora voicemail greeting message played to a contact based on the contactgroup to which the contact belongs. For example, a user may set a firstringtone for business contacts and a second ringtone for personalcontacts, enabling the user to identify the contact group to which acontact calling the user belongs. Likewise, a user may select a“whisper” signal such that, when a user has answered a first call andreceives a second call or a text message, the user is alerted to thereceived second call or text message by a soft audio signal thatotherwise doesn't detract from the first call. For the purposes ofsimplicity, the remainder of the description herein will reference amobile device associated with two phone numbers, a first associated witha personal contact group and a second associated with a business contactgroup.

Contacts can be classified as “personal” or “work” (and accordingly,assigned to the personal contact group or the work group) via thecontact management module 206 in a number of ways. For instance, for anincoming call, if a contact calls the user's work phone number orpersonal phone number, the contact can be classified as a “work contact”or a “personal contact”, respectively. If a user corresponds with acontact using his or her work or personal email address, the contact canbe classified as a “work contact” or a “personal contact”, respectively.For outgoing calls, a user can be prompted to press a button, provide acode, or speak a command after dialing an unknown contact's number inorder to classify the contact's number as work or personal. For example,a user can be prompted to press “1” to classify a contact as a personalcontact, and to press “2” to classify the contact as a work contact. Insome embodiments, upon dialing an unknown contact's phone number, thecontact management module 206 can query a user's personal contacts orwork contacts to determine if a personal contact or work contact haspreviously dialed the phone number and, in response to such adetermination, can classify the unknown contact as a personal or workcontact, respectively.

Periodically (e.g., every week or every day), the contact managementmodule 206 can provide a user 102 a with a list of prospective contactsthat has corresponded with the user 102 a from their personal or workemail addresses. The contact management module 206 determines whetherthe email address used by the user 102 a for correspondence with eachprospective contact is a personal or work address and classifies thecontact based on the address used by the user 102 a. The contactmanagement module 206 does not recommend a contact to a user forclassification when an email from a contact is deleted by the user 102a, either unopened or opened but with no further action taken. When acontact uses more than one address to correspond with the contact 102 a,the contact management module 206 can use the last address used or theaddress used for a majority of correspondence as the basis for theassignment. The contact management module 206 can identify phone numbersequences included in signature blocks in emails and can include thesenumbers in the prospective contact's record. The contact managementmodule 206 can check whether a user 102 a has called or received a callfrom the prospective contact. When a contact is already stored in user'scontacts but is not assigned as a personal or work contact, the CSFclassifies the contact based on the email address used incorrespondence.

The contact management module 206 presents the analysis results of theprospective users to the user 102 a. The user 102 a may reject or changethe classification of a prospective contact. When a user accepts aprospective contact, the contact management module 206 adds the contactto the user's contacts stored in the user and contact store 204 and/orthe user's contact list stored in the user's device. The contactmanagement module 206 also stores the contact group classification(e.g., a work contact or a personal contact) of the contact. In someembodiments, a user's contact group (e.g., work contacts, personalcontacts) may be shared with one or more other users who are in the samegroup (e.g., a company group, a family group). The unified communicationservice 106 displays associated contact information for inbound calls toa main or any individual number to the user 102 a.

In some embodiments, upon dialing an unknown contact's phone number, thecontact management module 206 queries a user's contact database orsocial media account to determine if the unknown contact's phone numberis associated with a contact within the contact database (such as apersonal or work email account's address book) or social media/socialnetwork account, and if so, determines if the contact within the contactdatabase or social media/social network account is a work contact or apersonal contact. For example, if a contact is associated with an emailaccount with a domain name associated with a user's employer, thecontact can be classified as a work contact, and if a contact isassociated with a “family relationship” in a social network, the contactcan be classified as a personal contact. It should be noted that uponregistering with the unified communication service 106, the contactmanagement module 206 can query the user's contact database, socialmedia account, or social network account in advance to classifypotential contacts as work contacts and personal contacts, such thatwhen the user calls a unknown contact number, the contact managementmodule 206 can identify a pre-classified contact associated with theunknown contact number, and can classify the unknown contact based onthe pre-classification. Furthermore, the contact management module 206creates a draft contact record including the number and any informationit has found for this contact. The contact management module 206 maystore the created draft contact record and enable a user to approve ordecline this contact as well as to edit or add the information for thiscontact.

In some embodiments, a user can select one of a work contact and apersonal contact as a default setting such that when the user calls newcontacts, the new contact is classified according to the select defaultclassification. Classified contacts can be subsequently reclassified bythe user, for instance via an interface presented by the contactmanagement module 206, or by entering a code or pressing a particularbutton after dialing the contact's phone number.

The outgoing call management module 208 manages outgoing calls includingvoice calls or video calls. The outgoing call management module 208 mayprovide an interface where a user may place an outgoing call. Theinterface may request the user to select a phone number associated witha mobile device of the user from which a call should be initiated andprepares the call using the selected number. For example, the outgoingcall management module 208 may ask the user to speak or press one tocall a recipient from the phone number associated with the businesscontact group or to speak or press two to call a recipient from thephone number associated with the personal contact group. The user mayalso call a recipient from the device's native call interface and theoutgoing call management module 208 manages the call according to thecontact type of the recipient, thus enabling a user to make a call withone of two phone numbers based on the contact type without requiring amodification to the user's mobile device. The contact type of therecipient may be determined by looking up the phone number associatedwith the recipient that the user calls in the user and contact store204. The phone number of the user associated with the contact group towhich the recipient belongs may be used to call the recipient. When thenumber selected by the user and the number associated with the contactgroup to which the recipient belongs conflict, the outgoing callmanagement module 208 confirms with the user which number to use. Theuser's call is routed to the recipient with caller ID informationidentifying the phone number of the user used to make the call,beneficially enabling a user to prevent, for example, business contactsform seeing a phone number of the user associated with the personalcontact group and vice versa.

When the recipient's phone number is unknown, the outgoing callmanagement module 208 asks the user to select a phone number of the userto use for making the call. The user has the ability to turn this prompton and off and to select a default number to use for unknown phonenumbers, in both cases with a single touch. A contact record may becreated and stored for the recipient and the recipient's number, and therecipient's contact type can be determined according to the phone numberfrom which the user calls the recipient. For example, if a user calls acontact for a first time using the business phone number associated withthe user, the contact and associated contact information can be storedas a business group contact within the user and contact store 204. Inaddition, the contact management module 206 creates a draft contactincluding the recipient's phone number and any information it has foundfor this contact. The contact management module 206 may store thecreated draft contact and enable a user to approve or decline thiscontact as well as to edit or add the information for this contact. Theoutgoing call management module 208 manages the outgoing call accordingto any user settings such as a setting associated with a contact groupto which a call recipient belongs. In some embodiments, when therecipient does not answer, the outgoing call management module 208 mayremind the user to call back the recipient after a predetermined timeperiod. The predetermined time period may be specified by the user oraccording to the contact type of the recipient.

FIG. 3 illustrates a sequence diagram of an exemplary outgoing call,according to one embodiment. A user Bob 102 a calls 302 a recipientAlice 102 b from his cellphone, which is linked to two numbers includinga work phone number and a personal phone number. Bob 102 a makes thecall from an interface provided by the unified communication service 106or the native dialer of his cellphone. Bob's cellphone service providerRabbit 104 a routes 304 Bob's call to Alice to the unified communicationservice 106. Rabbit 104 a routes 304 the call according to variouscommunication protocols, for example, Session Initiation Protocol(“SIP”). The unified communication service 106 (via, for example, theoutgoing call management module 208), identifies or classifies 306 thecontact type of Alice, for example, as business or personal. The unifiedcommunication service 106 assigns 308 a caller ID to the call based onthe determined contact type. For example, Bob's work phone number shouldbe used when Alice is determined to be a business contact and Bob'spersonal phone number should be used when Alice is determined to be apersonal contact. The unified communication service 106 provides 310 thecaller ID to Rabbit 104 a, for example, by routing the call with thecaller ID back to the Rabbit 104 a. Rabbit 104 a routes 312 the callwith the caller ID to Alice's service provider Giant 104 b. Giant 104 broutes 314 the call with the caller ID to Alice 102 b. When Aliceanswers, the call between Bob and Alice is set up involving a segment316 between Giant 104 b and Alice 102 b, a segment between Giant 104 band Rabbit 104 a, and a segment between Rabbit 104 a and Bob 102 a,according to various communication protocols. After the call is set up,Bob's and Alice's voice and/or images are communicated between Bob andAlice via Rabbit 104 a, the unified communication service 106, and/orGiant 104 b, according to various communication protocols. It should benoted that although the examples in this and the following figures aredescribed in terms of a business contact group and a personal contactgroup, the functionalities described in the examples applies equally toany other sets of contact groups, such as local and internationalgroups.

Referring back to FIG. 2, the incoming call management module 210manages incoming calls including voice calls or video calls. Theincoming call management module 210 may determine a call settingaccording to the caller's number. For example, the incoming callmanagement module 210 determines whether or not the user should benotified and how the user should be notified according to the caller.The incoming call management module 210 may provide an interface where auser may answer an incoming call. The interface may provide and requestthe user to respond (e.g., answer, reject, ignore, mute, or block) tothe incoming call by selecting or speaking a corresponding action. Theuser may also respond to an incoming call from the device's native callinterface and the incoming call management module 210 manages the callaccording to the caller. In one embodiment, the incoming call managementmodule 210 allows a user to block all incoming calls from unknownnumbers.

The phone number of the user associated with the contact group to whichthe caller belongs or the contact type of the caller may be used todetermine whether or not a call should be routed and how the user shouldbe notified. The incoming call management module 210 may determine thecontact type of the caller by looking up the caller's phone number fromthe user and contact store 204. Settings associated with that caller orcontact group may be determined similarly. For example, a call shouldnot be routed to the user when the caller, or the contact group of thecaller, is blocked by the user at the time when the user is beingcalled. Notification settings including ringtone, volume, vibration modeand level, response actions (e.g., answer, reject, mute, or respond bytext messages, instant messages, chats, or emails), user interfaces, orcall back reminders, may be determined according to the contact type andany settings associated with the caller, contact type, and/or contactgroup. Additional devices to alert the user and associated notificationsettings may be determined similarly.

When the caller's number is unknown, the incoming call management module210 may notify the user via a user interface for unknown numbers, whichin turn may enable the user to classify the caller as a work contact ora personal contact. A contact record for the caller may be created andstored within the user and contact store 204 based on the selection of acontact group for the caller by the user. The caller's contact type canbe determined according to the user's number that the caller has called.For instance, if the caller calls the phone number of the userassociated with the business contact group, the caller can be classifiedas a business group contact. The incoming call management module 210manages an incoming call according to any user setting such as a contactgroup's setting that is applicable to the caller. In some embodiments,when the user does not answer, the incoming call management module 210may, based on the contact group associated with the caller, remind theuser to call back the caller after a predetermined time period orrespond by text messages, emails, instant messages, or chat messages.Content of the text messages, emails, instant messages, or chat messagesmay be communicated to the user according to the contact type of thecaller.

FIG. 4 illustrates a sequence diagram of an exemplary incoming callmanagement module 210, according to one embodiment. Bob's phone connects402 with the service provider Rabbit 104 a. A caller Alice 102 calls 404Bob by dialing Bob's phone number, and Alice's service provider Giant104 b routes 406 Alice's call to Bob's service provider Rabbit 104 a.Rabbit routes 408 the call to the unified communication interface 106.The unified communication service 106, for example, the incoming callmanagement module 210, identifies or classifies 410 the contact type ofAlice as business or personal (for instance, based on whether Alice callBob's business number of personal number). The unified communicationservice 106 determines 412 a call setting based on the determinedcontact type. Whether or not Bob should be notified at Bob's phoneassociated with the number that Alice called, how to notify Bob on Bob'sphone, whether there are other device(s) additional to Bob's phone, andhow to notify Bob on those devices is determined based on the determinedcontact type. For example, a first ringtone should be used when Alice isdetermined to be a business contact and a second ringtone should be usedwhen Alice is determined to be a personal contact. The unifiedcommunication service 106 routes 414 the call with the call setting toRabbit 104 a (or with the identified contact type), which routes 418 thecall with the call setting to Bob 102 a at his phone. The unifiedcommunication service 106 may route 416 the call with the call settingto Bob at other devices determined. When Bob answers his phone, the callbetween Bob and Alice is set up involving a segment 410 between Bob 102a and Rabbit 104 a, a segment 422 between Rabbit 104 a and Giant 104 b,and a segment between Giant 104 b and Alice 102 b. After the call is setup, Bob's and Alice's voice and/or images are related between Bob andAlice via Rabbit 104 a, the unified communication service 106, and/orGiant 104 b, according to various communication protocols. In someembodiments, Bob's device receives the call from Alice, identifies acontact group associated with Alice (for instance based on a contacttype received from the unified communication service 106, or based oncontact groups stored locally at Bob's device), and alerts Bob to thecall based on the identified contact group (for instance, using avibration pattern for a business contact and a particular ringtone for apersonal contact).

Referring back to FIG. 2, the voicemail management module 212 managesvoicemails for unanswered (e.g., missed or rejected) incoming callsincluding voice calls or video calls. The voicemail management module212 may determine a voicemail setting according to the caller's contacttype. For example, the voicemail management module 212 determineswhether or not the user should be notified and how the user should benotified according to the contact type. The voicemail management module212 may provide an interface where a user may create, edit, and managevoicemail greeting messages and where the user may review a voicemailmessage. The interface may provide and request the user to respond(e.g., review, forward, ignore, delete, remind later, or block) to avoicemail message by selecting or speaking a corresponding action. Theuser may also respond to a voicemail message from the device's nativecall interface and the voicemail management module 212 manages the callaccording to the caller's contact type.

The number associated with the contact group to which the caller belongsor the contact type of the caller may be used to determine whether ornot and how the caller can leave a voicemail as well as whether or notand how a user should be notified. The voicemail management module 210may determine the contact type of the caller and settings associatedwith the caller by looking up the caller's phone number from the userand contact store 204. For example, a professional voicemail greetingmessage can be used when the caller is a business contact and a casualvoicemail greeting message can be used when the caller is a personalcontact.

Notification settings including ringtone, volume, vibration includingmode and level, response actions (e.g., review, forward, delete, remindlater, or respond by text messages, instant messages, chats, or emails),user interfaces, or call back reminders, may be determined according tothe contact type and any settings associated with the caller, contacttype, and/or contact group. In some embodiments, a notification settingincludes generating a transcription of a voicemail, and sending thetranscription to a user by email or SMS message. In some embodiments, anotification setting includes converting a voicemail message to an MMSmessage with a transcription and audio attachment (for instance, in theMP3 format), beneficially enabling a user to reply via SMS messageinstead of requiring the user to listen to the voicemail and respond viaa voicemail or dialer interface. In some embodiments, a user is notifiedby sending a notification via a mobile phone application. Additionaldevices or ways to alert the user and associated notification settingsmay be determined similarly.

When the caller's number is unknown, the voicemail management module 212may determine whether or not a caller can leave a voicemail and canselect a voicemail greeting message. A contact record may be created andstored for the user to store the caller and the caller's number. Thecaller's contact type can be determined according to the user's numberthat the caller has called. The voicemail management module 212 managesa voicemail message according to any user's setting such as a contactgroup's setting that is applicable to the caller. In some embodiments,the voicemail management module 212 may remind the user to call back thecaller after a predetermined time period or respond by text messages,emails, instant messages, or chat messages. The predetermined timeperiod may be specified by the user or according to the contact type ofthe caller.

FIG. 5 illustrates a sequence diagram of an exemplary voicemailmanagement module 212, according to one embodiment. Bob's phone connects502 with the service provider Rabbit 104 a. A caller Alice 102 b calls504 Bob by dialing a phone number associated with Bob's, and Alice'sservice provider Giant 104 b routes 506 Alice's call to Bob's serviceprovider Rabbit 104 a. Rabbit 104 a routes 508 the call to the unifiedcommunication interface 106. If upon ringing Bob's phone (as shown inFIG. 4), Bob doesn't answer the phone after a predetermined amount oftime (or if Bob elects to forward the call immediately to voicemail),the unified communication service 106, for example, the voicemailmanagement module 212 determines 512 a voicemail setting based on thedetermined contact type associated with the call. Whether or not thevoicemail box should be activated, which voicemail greeting message,whether Bob should be notified at Bob's phone associated with thevoicemail left by Alice, how to notify Bob on Bob's phone, whether thereare other device(s) additional to Bob's phone, and/or how to notify Bobon those devices are determined based on the determined contact type.For example, a first greeting message should be used when Alice isdetermined to be a business contact and a second greeting message shouldbe used when Alice is determined to be a personal contact. The unifiedcommunication service 106 routes 514 the call with the voicemail settingto Rabbit 104 a, which routes 516 the call with the voicemail setting toBob 102 a at his phone. When Bob fails to answer his phone, Rabbit 104 anotifies the unified communication service 106 that the call is failed,and the unified communication service 106 terminates 520 the call andinitiates to set up a voicemail. The unified communication service 106routes 522 the voicemail setup instruction with the voicemail setting toRabbit 104 a, which routes 524 the voicemail setup instruction with thevoicemail setting to Giant 104 b, which routes 526 the voicemail setupinstruction with the voicemail setting to Alice 526. Alice leaves 528 avoicemail, which the unified communication service 106 may notify Bob102 a according to the determined voicemail setting. In someembodiments, when Bob's phone is not connected with Rabbit 104 a, Rabbit104 a cannot find Bob's phone and notifies the unified communicationservice 106 that call to Bob has failed.

The text management module 214 manages outgoing and incoming textmessages including SMSs and MMSs. The text management module 214 maymanage outgoing and incoming text messages according to the recipientand the sender, respectively. For example, the text management modulemay determine a number from which to send a text message according tothe recipient. The text management module 214 may determine a textmessage setting according to the text message sender's number. Forexample, the text management module 214 determines whether or not theuser should be notified and how the user should be notified according tothe text message sender. The text message module 214 may provide aninterface where a user may edit and send a text message as well asreview and respond to a text message. For outgoing text messages, theinterface may request the user to select a number from which to send atext message. The user may also send a text message to a recipient fromthe device's native text message interface and the text managementmodule 214 manages the text message according to the contact type of therecipient. The contact type of the recipient may be determined bylooking up the number the user texts in the user and contact store 204.The number of the user associated with the contact group to which therecipient belongs or the contact type of the contact may be used to textthe recipient. When the number selected by the user and the numberassociated with the contact group to which the recipient belongsconflict, the text management module 214 confirms with the user whichnumber to use. The user's text message or a push notification on isrouted to the recipient with the caller ID unless the caller ID isotherwise disabled by the user.

When the recipient's number is unknown, the text management module 214prompts the user to determine a number to use for sending a textmessage. The text management module 214 temporarily stores the sent SMSand replies via SMS to the user requesting whether to treat therecipient as a business contact or a personal contact. This SMSconversation happens between the text management module 214 and the userto determine which contact group to use and should be completed within aspecific time period (30 seconds for example) or the original SMS willbe sent with the default contact group. The user can turn this prompt onand off, and can also set a number to use as a default for unknownnumbers. A contact record may be created and stored for the user tostore the recipient and the recipient's number, during which process,the recipient's contact type can be determined according to the numberfrom which the user texts the recipient. The recipient may be assignedto a contact group according to the number from which the user texts therecipient. The outgoing call management module 208 manages the outgoingcall according to any user's setting such as a contact group's settingthat is applicable to the recipient.

For incoming text messages, the interface may provide and request theuser to respond (e.g., retrieve, review, reply, delete, forward, or sendread receipts) to an incoming text message by selecting or speaking acorresponding action. The user may also respond to an incoming textmessage from the device's native text message interface and the textmanagement module 214 manages the text message according to the caller.The text management module 214 may determine a text message settingaccording to the sender's number or contact type. For example, the textmanagement module 214 determines whether or not the user should benotified and how the user should be notified according to the sender'scontact type. The number associated with the contact group to which thesender belongs or the contact type of the sender may be used todetermine whether or not the sender's text message should be routed andwhether or not and how a user should be notified are determined by thecontact type of the sender and any settings associated with that sender.The text management module 214 may determine the contact type of thesender by looking up the sender's phone number from the user and contactstore 204, or by determining whether the sender texted the user's phonenumber associated with the business contact group or the personalcontact group. Settings associated with that sender may be determinedsimilarly. Notification settings including ringtone, volume, vibrationincluding mode and level, response actions (e.g., review, forward,delete, remind later, send read receipts, or respond by text messages,instant messages, chats, or emails), or user interfaces, may bedetermined according to the contact type and any settings associatedwith the sender, contact type, and/or contact group. Additional devicesor ways to alert the user and associated notification settings may bedetermined similarly.

When the sender's number is unknown, the text management module 214 maynotify the user via a user interface for unknown numbers. A contactrecord may be created and stored for the user to store the sender andthe sender's number. The sender's contact type can be determinedaccording to the user's number to which the sender sends a text message.The text management module 214 manages an incoming text messageaccording to any user's setting such as a contact group's setting thatis applicable to the caller. In some embodiments, when the user does notreply, the text management module 214 may remind the user to respond tothe sender after a predetermined time period and/or responding by calls,text messages, emails, instant messages, or chat messages. Thepredetermined time period may be specified by the user or according tothe contact type of the sender. Content of the text messages, emails,instant messages, or chat messages may be specified by the user oraccording to the contact type of the sender.

In some embodiments, the text management module 214 can route textmessages differently based on the classification of a contact. Forinstance, for text messages sent to and received from personal contacts,the text management module 214 can route the text messages directly toand from a user's device (via the device's native text messagingapplications) without routing the text messages through or exposing thetext messages to the user's employer. Similarly, for text messages sentto and received from work contacts, the text management module 214 canroute such text messages through the employer's servers or through anapplication at the unified communication service 106. In suchembodiments, a user's employer can incorporate such text messages intocustomer relationship management (“CRM”) processes, enabling the user'semployer to potentially access such text messages, for instance for thepurpose of creating business records or documents, for communicationmanagement purposes, for enabling customer support of the user, and thelike. In some embodiments, an application associated with the unifiedcommunication service 106 can run on the user's device, and can directlyreceive such text messages. In these embodiments, the application cannotify the user of a new text message from a work contact (beneficiallyenabling the user to identify when a text message from a work contact isreceived), and can route the text message to the device's nativemessaging application, enabling the user to access text messages fromboth personal contacts and work contacts within the same interface.

In some cases (for instance, where a user's device is an IPHONE®), thetext management module 214 may route text messages via a device-specificmessaging server (such as iMessage) when both the sender device andrecipient devices are determined to be IPHONES®. The text managementmodule 214 may only allow text messages being routed via iMessage whenthe recipient is a personal contact of the sender's. The text messagemodule 214 may prevent text messages from being routed via iMessage whenthe recipient is a business contact of the sender's. This is becauseiMessage is a private communication channel and best suited for personalcommunication. Messages exchanged with contacts in the business groupare only routed via the unified communication service 106, and messagesexchanged with contacts in the personal group are routed via the unifiedcommunication service 106 as well as, optionally, a native interface(e.g., iMessage). As such, the unified communication service 106 mayintegrate business processes to exchange messages with businesscontacts. For example, in some embodiments, the unified communicationservice 106 allows using business processes such as CRM to exchangemessages with business contacts. In some embodiments, the unifiedcommunication service 106 delivers messages exchanged with contacts asdata but free of data roaming charges. For example, for users who are ona roaming network, the unified communication service 106 may allowcommunication to this business message delivery mechanism free ofroaming charges by allowing data communications with those servers whenthe user is in the roaming network even if the user has turned off dataroaming, provided the user has not also turned off voice and SMSroaming.

FIG. 6 illustrates a sequence diagram of an exemplary text managementmodule 214, according to one embodiment. A user Bob 102 a sends 602 aSMS to a recipient Alice 102 b from his cellphone which is linked to twonumbers including a work phone number and a personal phone number. Bob102 a sends the SMS from an interface provided by the unifiedcommunication service 106 or the native messaging interface of hiscellphone. Bob's cellphone service provider Rabbit 104 a routes 604Bob's SMS to Alice to the unified communication service 106. Rabbit 104a routes 604 the SMS to the unified communication service 106 accordingto various communication protocols, for example, Short MessagePeer-to-Peer (“SMPP”). The SMS may be routed to a Short Message ServiceCenter (“SMSC”) provided by the unified communication service 106. Theunified communication service 106, for example, the text managementmodule, identifies or classifies 606 the contact type of Alice, forexample, as business or personal. The unified communication service 106assigns 608 a caller ID based on the determined contact type. Forexample, Bob's work phone number should be used when Alice is determinedto be a business contact and Bob's personal phone number should be usedwhen Alice is determined to be a personal contact. The unifiedcommunication service 106 routes 610 the SMS with the caller ID toRabbit 104 a. Rabbit 104 a routes 612 the SMS with the caller ID toAlice's service provider Giant 104 b. Giant 104 b delivers the SMS withthe caller ID to Alice 102 b. It should be noted that in someembodiments, the unified communication service 106 routes the SMS withthe caller ID directly to Giant 104 b (without first routing throughRabbit 104 a). Similarly, the unified communication service 106 canroute the SMS with the caller ID to a different service provider, or toa 3^(rd) party messaging service that in turn forwards the message toAlice 102 b.

FIG. 7 illustrates a sequence diagram of an exemplary text managementmodule 214, according to one embodiment. A sender Alice 102 b sends 702an SMS to Bob at Bob's phone number, and Alice's service provider Giant104 b routes 704 the SMS to Bob's service provider Rabbit 104 a. Rabbit104 a routes 706 the SMS to the unified communication interface 106,according to various communication protocols, for example, Short MessagePeer-to-Peer (“SMPP”). The SMS may be routed to a Short Message ServiceCenter (“SMSC”) provided by the unified communication service 106. Theunified communication service 106, for example, the text managementmodule 214 identifies or classifies 708 the contact type of Alice, forexample based on whether Alice sent a message to Bob's work phone numberor home phone number. The unified communication service 106 determines710 an SMS setting based on the determined contact type. Whether or notthe SMS should be routed to Bob, whether Bob should be notified at Bob'sphone, how to notify Bob on Bob's phone, whether there are otherdevice(s) additional to Bob's phone and how to notify Bob on thosedevices are determined based on the type of contact of Alice. Theunified communication service 106 routes 712 the SMS with the SMSsetting to Rabbit 104 a, which routes 714 the SMS with the SMS settingto Bob 102 a at his phone. When Bob's phone is offline, Rabbit 104 a maytry to deliver the SMS to Bob for a predetermined time period, afterwhich Rabbit 104 a may notify the unified communication service 106 thatdelivering the SMS to Bob has failed.

FIG. 8 illustrates a sequence diagram of an exemplary text managementmodule 214, according to one embodiment. A user Bob 102 a sends 802 aMMS to a recipient Alice 102 b from his cellphone which is linked to twonumbers including a work phone number and a personal phone number. Bob102 a sends the MMS from an interface provided by the unifiedcommunication service 106 or the native dialer of his cellphone. Bob'scellphone service provider Rabbit 104 a routes 804 Bob's MMS to Alicenotification with headers to the unified communication service 106. Theunified communication service 106, for example, the text managementmodule, identifies or classifies 806 the contact type of Alice, forexample, as business or personal. The unified communication service 106assigns 808 a caller ID based on the determined contact type and updatesthe MMS notification header with the caller ID. For example, Bob's workphone number should be used when Alice is determined to be a businesscontact and Bob's personal phone number should be used when Alice isdetermined to be a personal contact. The unified communication service106 provides 810 the MMS notification with the updated header to Rabbit104 a. Rabbit 104 a delivers 812 the MMS with the updated header toAlice's service provider Giant 104 b, for example, according to an MMSarchitecture standard. Giant 104 b sends 814 the MMS WirelessApplication Protocol (WAP) push notification to Alice 102 b. Alice 102 bretrieves 814 the MMS from Giant 104 b, for example, a MMS center.

FIG. 9 illustrates a sequence diagram of an exemplary text managementmodule, according to one embodiment. A sender Alice 102 b sends 902 anMMS to Bob at Bob's phone number, and Alice's service provider Giant 104b routes 904 the MMS to unified communication service 106, for example,over MM4 by using Service Provider ID (SPID) of unified communicationservice 106. Alice's MMS push notification may also be routed to unifiedcommunication service 106, for example, to the SMSC provided by theunified communication service 106 via SMPP. The unified communicationservice 106, for example, the text management module 214 identifies orclassifies 906 the contact type of Alice, for example, as business orpersonal. The unified communication service 106 updates 908 the pushnotification according to the identified contact type. The unifiedcommunication service 106 routes 910 the updated MMS push notificationto Rabbit 104 a, which routes 912 the updated MMS push notification toBob 102 a at his phone. When Bob's phone is offline, Rabbit 104 a maytry to deliver the updated MMS push notification to Bob for apredetermined time period, after which Rabbit 104 may notify the unifiedcommunication service 106 that delivering the MMS push notification toBob has failed. Bob 102 a retrieves 912 the MMS from the unifiedcommunication service 106.

Referring back to FIG. 2, the billing management module 216 managesbilling for various communication services provided to billing accounts.A billing account stored in the billing account store 220 may beassociated with one or more user accounts stored in the user and contactstore 204. For example, a corporate billing account may be associatedwith a corporate entity's account, which in turn is associated withmultiple employee user accounts. The billing management module 216tracks and monitors the usage of various communication services todevices associated with various user accounts and determines billingbased on the monitored usage and a corresponding policy plan. Forexample, the billing management module 216 can track and monitor callusage, text usage, or data plan usage for the unified communication IDs,the device IDs, and the virtual device IDs. For example, for a user'sphone linked to a work number associated with a virtual device ID or theunified communication ID and a personal number associated with thedevice ID, the billing management module 216 may track and monitorvarious (e.g., personal, business, domestic, international, roaming,etc.) usages for the work phone number and for the personal number andprovide separate billings based on the monitored usage.

FIG. 10 illustrates a sequence diagram of an exemplary billingmanagement module 216, according to one embodiment. Bob 102 a requests1002 access to a social network on his phone, which is sent to hisservice provider Rabbit 104 a. Rabbit 104 a routes 1004 the IP packetsto the unified communication service 106, which queries 1006 a billingpolicy that classifies social network activity as personal activity, andassigns 1007 this activity to personal billing. The unifiedcommunication service 106 processes 1008 traffic and routes the requestto the social network 650. The social network 650 provides 1010 accessand social network data to the unified communication service 106, whichprovides 1012 the social network data to Rabbit 104 a, which in turnprovides 1014 the social network data to Bob 102 a.

The billing management module 216 enables a network administrator,employer account administrator, or the like to create one or morebilling policies to govern a user's device usage and to route expensesrelated to such usage to the appropriate account (such as a work accountpaid for by an employer, or a personal account paid for by the user). Insome embodiments, a billing policy can identify a contact group (such as“work contacts”) or a set of numbers associated with a work account suchthat calls to work-related numbers are paid for by the employer, whilecalls to other numbers are paid for by the user. Billing policies canalso identify an amount of data a user can send and receive via a workaccount, such that an employer will pay for data up to the identifiedamount, and the user will pay for the remainder of data used (forinstance, within a billing period). Billing policies can likewiseidentify a number of calling minutes and/or text messages that arecovered by a work account (and thus paid for by an employer), such thatcall time or text messages over the identified thresholds are billed toa personal account (and thus paid for by the user).

Billing policies can also specify particular URLs or websites, and canroute costs incurred with navigating to the specified URLs and websitesto a particular account (such as a work account). Likewise, billingpolicies can blacklist particular URLs or websites, such that costsincurred with navigating to the blacklisted URLs and websites areprevented from being routed to a particular account (such as a workaccount) and are instead routed to a different account (such as apersonal account). Billing policies can also specify otherservices/charges, and can specify a particular account which to routecharges associated with the specified services/charges. Examples of suchservices/charges include roaming charges, map or navigation services,email services, text or SMS charges, app services or charges, and thelike.

Referring back to FIG. 2, the privacy management module 218 managesprivacy settings for various communication services. The privacymanagement module 218 may provide a user interface, via which a user maymake various communications private to other users. For example, a usermay make phone calls, text messages, web activities private such thatthe communications are secured, not recorded, and only accessible by theuser. For example, a user's phone is linked to a work number associatedwith a virtual device ID or unified communication ID and a personalnumber associated with the device ID, and the user may classify allcommunications associated with the personal number as private and notsubject to access by the user's employer. In such embodiments, even if auser's employer provides a billing policy that enables and pays for theuser to access, for example, a social network, the user may insteadselect to keep such activity private, hiding access to the socialnetwork from the user, but requiring that the user pay for data chargesassociated with the access to the social network.

The home number management module 222 can enable multiple phones, suchas phones belonging to members of a family, to share a phone number. Thehome phone number is in addition to a user's personal and work phonenumbers. A user can register a home phone number with the unifiedcommunication service 106 via the user management module 202, which inturn can assign a second virtual device ID to a user's device, and canassociate the home phone number with the second virtual device ID. Theuser can then, via the home number management module 222, associate thehome phone number with devices of family members, which in turn areassigned virtual device IDs, which are then associated with the homephone number. In other words, the home number management module 222enables multiple users to receive calls made to the same number,emulating the traditional family/household land line phone number.

The home number management module 222, in response to receiving a callto a home phone number of a group of users, can ring all phones sharingthe home phone number. In some embodiments, when one user in the groupof users answers the call, the phones of the other users in the group ofusers stop ringing. In some embodiments, when a user in the group ofusers answers the call, the user is prompted to either answer the callor divert the call to voicemail. In response to the user selecting todivert the call to voicemail, the phones of the other members of thegroup of users continue to ring until one user opts to answer the call.If all users in the group of users opt to divert the call to voicemail,or if no user opts to answer the call within a pre-designated amount oftime, the call is routed to voicemail.

The home number management module 222, in response to the creation of avoicemail by a contact calling a home phone number, can store thevoicemail in the voicemail inboxes of one or more users sharing the homephone number. For instance, the voicemail can be left in the voicemailinbox of the head of household or of the user that initially registeredthe home phone number; alternatively, every user sharing the home phonenumber can receive the voicemail in their inbox. In some embodiments,the home number management module 222 routes the voicemail to a sharedvoicemail inbox accessible to all users that share the home phonenumber. In such embodiments, if one user deletes the voicemail, theother users sharing the shared inbox can no longer access the voicemail.

In some embodiments, the home number management module 222 identifiescalls to the home phone as home calls, enabling devices of users sharingthe home phone number to ring using a ringtone, vibration pattern, orother notification dedicated to calls to the home phone number. The homenumber management module 222 can direct calls to the home phone numberdirectly to the devices of the users associated with the home phonenumber, preventing (for example) a user's employer from intercepting orotherwise being notified about the calls.

The business integration module 224 may allow integration with businesssoftware or interfaces such as customer relationship management (CRM)systems. Business communication, as a result, can be accessed andtracked by the integrated systems. A user (e.g., a person or entity) mayconfigure an account with a selected CRM system and application programinterface (API) credentials to access the selected CRM system. Thebusiness integration module 224 may automatically integrate businesscommunication (e.g., communication with a business CRM contact, lead, oraccount) into the selected CRM system. The business integration module224 may 1) record that a call is made or received, and whether it isanswered; 2) record calls made and store the recorded audio; 3) recordcalls made, transcribe the audio into text, store the text, and make thecall text searchable and analyzable; 4) store text messages received andsent as individual events or as conversations within a given timespan;or 5) store voicemails received and optionally transcribe them.

The business integration module 224 may further provide a businesssoftware or system interface that allows a user to interact withbusiness contacts using their mobile phone and/or mobile phone number,from the business software or system interface. The business integrationmodule 224 may establish a communication connection with a user prior tocontacting the user's business contact. For example, the businessintegration module 224 may call the user's cellphone number to establisha connection or to use a virtual version of their mobile phone as a webapplication (for instance, via webRTC) to communicate to the unifiedcommunication service 106. The business integration module 224 may thencontact the user's business contact to establish a communication channelbetween the user and the user's business contact via the unifiedcommunications service 106. A user may continue a voice or textconversation from the interface, which may open up a window surfacingrecent or all communications up to date with that business contact. Insome embodiments, all communication with the business contact from allemployees associated with an entity may be aggregated and presented to auser. The full extent of communications including conversations ormessaging threads across the entity with a business contact may bepresented to users that are associated with the entity and authorized toview such communications. As such, different users may communicate witha business contact via a shared number (e.g., a sales number or acustomer support number).

Upon reading this disclosure, those of skill in the art will appreciatestill additional alternative designs for a unified communicationinterface providing various communication services. Thus, whileparticular embodiments and applications of the present disclosure havebeen illustrated and described, it is to be understood that theembodiments are not limited to the precise construction and componentsdisclosed herein and that various modifications, changes and variationswhich will be apparent to those skilled in the art may be made in thearrangement, operation and details of the method and apparatus of thepresent disclosure disclosed herein without departing from the spiritand scope of the disclosure as defined in the appended claims.

What is claimed is:
 1. A computer-implemented method for managingvoicemail, comprising: receiving, at an intermediate servercommunicatively coupled to a mobile phone associated with a first phonenumber corresponding to a first contact group and a second phone numbercorresponding to a second contact group, a request to receive anincoming call associated with a caller phone number, the requestcorresponding to the first phone number or the second phone number; inresponse to receiving the request to receive the incoming call,identifying, by the intermediate server, a contact group associated withthe request, the identified contact group comprising the first contactgroup in response to the received request corresponding to the firstphone number and the second contact group in response to the receivedrequest corresponding to the second phone number, the first contactgroup and the second contact group each including one or more phonenumbers; identifying, by the intermediate server, a voicemail settingassociated with the identified contact group, the voicemail settingconfigured by a user of the mobile device in advance of receiving therequest, the voicemail setting defining a first notification forplayback to the user and a second notification for playback to a caller;modifying, by the intermediate server, the request to receive theincoming call to include the voicemail setting; and in response to adetermination to route the incoming call to voicemail, configuring thevoicemail based at least in part on the voicemail setting.
 2. The methodof claim 1, wherein the first phone number comprises a phone numbercorresponding to hardware of the mobile phone, and wherein the secondphone number comprises a virtual phone number assigned to the mobilephone by the intermediate server.
 3. The method of claim 1, whereinidentifying the contact group associated with the request comprisingidentifying the contact group associated with the phone number which therequest corresponds.
 4. The method of claim 1, wherein the secondnotification comprises a first voicemail greeting message in response tothe identified contact group comprising the first contact group and asecond voicemail greeting message in response to the identified contactgroup comprising the second contact group.
 5. The method of claim 1,wherein the first notification comprises a determination to immediatelyroute the incoming call to voicemail without first routing the incomingcall to the mobile device.
 6. The method of claim 1, wherein the firstnotification comprises a type of notification signal for the mobiledevice to emit to indicate that a voicemail message corresponding to theincoming call is received.
 7. The method of claim 1, wherein the firstnotification comprises a determination of whether or not the mobilephone emits a voicemail notification signal in response to receiving avoicemail message corresponding to the incoming call.
 8. Anon-transitory computer-readable storage medium storing executablecomputer instructions for managing voicemail, the instructions, whenexecuted by a hardware processor, configured to perform stepscomprising: receiving, at an intermediate server communicatively coupledto a mobile phone associated with a first phone number corresponding toa first contact group and a second phone number corresponding to asecond contact group, a request to receive an incoming call associatedwith a caller phone number, the request corresponding to the first phonenumber or the second phone number; in response to receiving the requestto receive the incoming call, identifying, by the intermediate server, acontact group associated with the request, the identified contact groupcomprising the first contact group in response to the received requestcorresponding to the first phone number and the second contact group inresponse to the received request corresponding to the second phonenumber, the first contact group and the second contact group eachincluding one or more phone numbers; identifying, by the intermediateserver, a voicemail setting associated with the identified contactgroup, the voicemail setting configured by a user of the mobile devicein advance of receiving the request, the voicemail setting defining afirst notification for playback to the user and a second notificationfor playback to a caller; modifying, by the intermediate server, therequest to receive the incoming call to include the voicemail setting;and in response to a determination to route the incoming call tovoicemail, configuring the voicemail based at least in part on thevoicemail setting.
 9. The non-transitory computer-readable storagemedium of claim 8, wherein the first phone number comprises a phonenumber corresponding to hardware of the mobile phone, and wherein thesecond phone number comprises a virtual phone number assigned to themobile phone by the intermediate server.
 10. The non-transitorycomputer-readable storage medium of claim 8, wherein identifying thecontact group associated with the request comprising identifying thecontact group associated with the phone number which the requestcorresponds.
 11. The non-transitory computer-readable storage medium ofclaim 8, wherein the second notification comprises a first voicemailgreeting message in response to the identified contact group comprisingthe first contact group and a second voicemail greeting message inresponse to the identified contact group comprising the second contactgroup.
 12. The non-transitory computer-readable storage medium of claim8, wherein the first notification comprises a determination toimmediately route the incoming call to voicemail without routing theincoming call to the mobile device.
 13. The non-transitorycomputer-readable storage medium of claim 8, wherein the firstnotification comprises a type of notification signal for the mobiledevice to emit to indicate that a voicemail message corresponding to theincoming call is received.
 14. The non-transitory computer-readablestorage medium of claim 8, wherein the first notification comprises adetermination of whether or not the mobile phone emits a voicemailnotification signal in response to receiving a voicemail messagecorresponding to the incoming call.
 15. A system for managing voicemail,comprising: an intermediate server communicatively coupled to a mobilephone associated with a first phone number corresponding to a firstcontact group and a second phone number corresponding to a secondcontact group, the intermediate server comprising one or more hardwareprocessors configured to: receive a request to receive an incoming callassociated with a caller phone number, the request corresponding to thefirst phone number or the second phone number; in response to receivingthe request to receive the incoming call, identify a contact groupassociated with the request, the identified contact group comprising thefirst contact group in response to the received request corresponding tothe first phone number and the second contact group in response to thereceived request corresponding to the second phone number, the firstcontact group and the second contact group each including one or morephone numbers; identify a voicemail setting associated with theidentified contact group, the voicemail setting configured by a user ofthe mobile device in advance of receiving the request, the voicemailsetting defining a first notification for playback to the user and asecond notification for playback to a caller; modify the request toreceive the incoming call to include the voicemail setting; and inresponse to a determination to route the incoming call to voicemail,configure the voicemail based at least in part on the voicemail setting.16. The system of claim 15, wherein the first phone number comprises aphone number corresponding to hardware of the mobile phone, and whereinthe second phone number comprises a virtual phone number assigned to themobile phone by the intermediate server.
 17. The system of claim 15,wherein identifying the contact group associated with the requestcomprising identifying the contact group associated with the phonenumber which the request corresponds.
 18. The system of claim 15,wherein the second notification comprises a first voicemail greetingmessage in response to the identified contact group comprising the firstcontact group and a second voicemail greeting message in response to theidentified contact group comprising the second contact group.
 19. Thesystem of claim 15, wherein the first notification comprises adetermination to immediately route the incoming call to voicemailwithout routing the incoming call to the mobile device.
 20. The systemof claim 15, wherein the first notification comprises a type ofnotification signal for the mobile device to emit to indicate that avoicemail message corresponding to the incoming call is received. 21.The system of claim 15, wherein the first notification comprises adetermination of whether or not the mobile phone emits a voicemailnotification signal in response to receiving a voicemail messagecorresponding to the incoming call.